home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Grand Slam 3
/
Grand Slam 3.iso
/
002
/
badsc102.arj
/
BADSCAN.DOC
< prev
next >
Wrap
Text File
|
1995-03-14
|
5KB
|
111 lines
─────────────────────────────────────────────────────────────────────────────
▄▄███▄ ▄█ ██▄ ▄███▄ ▄█ ██▄ ██▄ ▄▄███▄ ▄███▄ ▄█ ██▄ ██▄
██▀██ ▀ ██ ██▄ ▄█▀ ██ ▀ ██▀█▄ ██ ██▀ ██ ▄█▀ ██ ▀ ██▀█▄ ██
▀█▄ ██ ██ ██ ▄███ ██▄ ██ ▀███▄ ██▄ ▄█▀ ██ ▄███ ██▄ ██ ▀███▄
██ ██ █ ██ ██▄█▀ ██ ▀██ ▀██ ▄██ ██▀██▀ ██▄█▀ ██ ▀██ ▀██ ▄██
██ ▀█▀█▀ ██▀ ██ ██ ██ ██ ██ ██▀ ██ ██ ██ ██
▀█ ═════════════════════════════════════ ▀█ ════════════════════════════
Cederdreef 46 ▄▀▀ ▄▀▄ ▄▀▀ ▀█▀ █ █ ▄▀▄ █▀▄ ▄▀▀
3137 PB Vlaardingen ▀▄ █ █ █▀ █ █ █ █ █▀█ █▀▄ █▀
The Netherlands ▀▀ ▀ ▀ ▀ ▀ ▀ ▀ ▀ ▀ ▀ ▀▀
FIDO: 2:281/629.4
─────────────────────────────────────────────────────────────────────────────
B A D S C A N - Automated BadUserList Processor
Version 1.02Γ
Copyright (c) 1995 by TWAiN PAiN Software
Written By Alex Paalvast
┌─────────────────────────────────────────────────────────────────────────────┐
│ ░░░░░░░░░░░░░░░░░░░░░░░░░░░ (I) What is BadScan ░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└─────────────────────────────────────────────────────────────────────────────┘
BadScan is used by the sysops of the BBSes which are
connected to a net. BadScan's only purpose is to process
a file wich is send by the HQ. This file holds all users
which are considered bad on a net. This list must be
generated by BadMan.
IMPORTANT:
This product is freeware. You only have to pay for the BadMan
utility which is used by the moderator of a net. If you are
not the moderator but just a simple sysop there is no need to
worry about registering BadScan.
┌─────────────────────────────────────────────────────────────────────────────┐
│ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░ (II) Installation ░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└─────────────────────────────────────────────────────────────────────────────┘
To install BadScan in your system you should first consider
which flags will be affected by BadScan. To tell BadScan
which flags should be changed run:
BADSCAN /Setup
This allows you to change all flagsettings. Don't be scared
off by the amount of flags which are presented to you.
Now enter all the flagchanges. You must be aware that
always ALL bad users are resend on a change. If you change
the flagsettings of a bad user manually via RemoteAccess,
a new sending of the baduserlist will put the flagsettings
back in their 'BAD' state as presented here.
┌─────────────────────────────────────────────────────────────────────────────┐
│ ░░░░░░░░░░░░░░░░░░░░░░░░░ (III) Usage of BadScan ░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└─────────────────────────────────────────────────────────────────────────────┘
The netmoderator must specify a file-area in which the
baduserlist is send. Use BadScan in the event run after
receiving mail or at a nightly (but Daily) maintenance
event. You must specify which file must be processed. This
file is placed in the selected file-area, so you must know
the path to the area. The name of the file is chosen by the
moderator but always ends with .BAD. (e.g. DIGITAL.BAD)
Put in a line in the batchfile like:
BADSCAN <file-area-path>\<filename>
E.G. if your file-area is located in directory
D:\AREAS\BIGBRO\GENERAL\, your network is called
BigBrotherNetwork and the filename chosen by the moderator
is 'BIGBRO' then the commandlike would look like:
BADSCAN D:\AREAS\BIGBRO\GENERAL\BIGBRO.BAD
Be aware, that if you want to use BadScan for a number of
networks, say N, you must use N different copies of
BadScan. This it due to the fact that only one config-file
may be available at a time.
┌─────────────────────────────────────────────────────────────────────────────┐
│ ░░░░░░░░░░░░░░░░░░░░░░░░ (IV) Commandline of BadScan ░░░░░░░░░░░░░░░░░░░░░░ │
└─────────────────────────────────────────────────────────────────────────────┘
The commandline looks like this:
BADSCAN /Setup
or
BADSCAN <baduserlist> [/1]
In the first case, the setup utility will be started, which
allows you to change the flagsettings.
The second case processes the selected baduserlist. This
file HAS to be created by BadMan.
The /1 parameter MUST be present if you run RemoteAccess 1.11.
WARNING:
Do not run BADSCAN in RA2.00 mode if you run RA1.11 or vice
versa. This will most likely trash your entire userdatabase!